-
Notifications
You must be signed in to change notification settings - Fork 595
Support for scala 2.13.0-M5 #2298
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Test FAILed. |
c35f898
to
d534d3b
Compare
Test FAILed. |
akka-http-core/src/main/scala-2.13.0-M5/akka/http/ccompat/package.scala
Outdated
Show resolved
Hide resolved
Is that documented somewhere? Would be nice if no overload was necessary at all and the compiler would just accept a Seq in the first place even without the We could also say that we don't keep source compatibility and remove the |
Test FAILed. |
@jrudolph do you think we should only support the varargs variant for 2.13 and deprecate the |
Test FAILed. |
Test FAILed. |
Test FAILed. |
Test PASSed. |
Test PASSed. |
Test PASSed. |
5c78251
to
75abac5
Compare
Test PASSed. |
Updated just akka-http-core on 2.12/2.13 for now.
Unfortunately we have a number of places where we have both a
varargs
and aimmutable.Seq
overload for the same method. This is no longer valid on 2.13.0, and the only way I could think of to solve this in a binary compatible way was a rather weird trick: introduce aVASeq
type which corresponds toimmutable.Seq
on 2.12 andimmutable.Iterable
on 2.13 (to avoid the ambiguity but at the same time be mostly source-compatible and keep intact the fact that this value is immutable).